Meta-data compliance
| Characteristic Name: | Meta-data compliance |
| Dimension: | Validity |
| Description: | Data should comply with its metadata |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of meta-data violations reported in an attribute per thousand records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Domains should be specified by considering all possible value patterns, cases and usage needs which is applicable for a data attribute. | (1) Eg: It is easy to maintain the order number as a numeric value since it can be easily incremented (10000, 10001, and 10002). But it can be also defined as alphanumeric in order to distinguish special cases (10000R is a return order of sales order 10000) |
| Maintain valid values/value ranges/Value lists for attributes. | (1) Gender can be M or F (2) Country is taken from the existing list of countries (3) Birth date cannot be a future value. (4) Salary range for level 4 employees must be between $40000-60000 |
| Usage of number ranges for critical data elements | (1) Sales orders 10000001 to 1999999 (2) Purchase orders 50000001 to 59999999 |
| Maintain the possible synonyms and abbreviations which could be accepted as valid values | (1) Post Box , PO BOX, BOX etc. |
| Explicitly mention what values, characters are not permitted in the attribute | (1) User Name can contain only A-Z (2) No blank spaces are allowed for credit card number |
| Explicitly mention the minimum /maximum number of characters, or any other requirements such as case sensitivity, that an attribute value should meet | (1) Password should contain minimum of 8 characters including one numeric and one capital |
| Maintain values based on specific formats as defined by the stakeholders, standards, best practices or agreements. | (1) Time should be in 24 hour clock (2) Date should be in DD/MM/YYYY |
| Appropriate measurement scale should be maintained against quantities and volumes | (1) Currency for Price values Kg/g/mg for weights litres for volumes (2) Data Dictionary , Data catalog |
| Documentation for Meta-Data is available online for the users | (1) Data Dictionary , Data catalog |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to define meta-data |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| 1) A new year 9 teacher, Sally Hearn (without a middle name) is appointed therefore there are only two initials. A decision must be made as to how to represent two initials or the rule will fail and the database will reject the class identifier of “SH09”. It is decided that an additional character “Z” will be added to pad the letters to 3: “SZH09”, however this could break the accuracy rule. A better solution would be to amend the database to accept 2 or 3 initials and 1 or 2 numbers.
2) The age at entry to a UK primary & junior school is captured on the form for school applications. This is entered into a database and checked that it is between 4 and 11. If it were captured on the form as 14 or N/A it would be rejected as invalid. |
N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
| the answer to the query “What is Mr. Wat- son% telephone number?” can bl: validated against the format for telephone numbers. Additionally, Wat- son’s address might be used to vallidate the area code and exchange | M. Brodie, “Data Quality in Information Systems”, North-Holland Publishing Company Information and Management 3, 1980, pp. 245-258. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Determines the extent to which data conforms to a specified format. For example, the order date must be in the format YYYY/MM/DD. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| 1) Data element passes all edits for acceptability and is free from variation and contradiction based on the condition of another data element (a valid value combination).
2) The metadata of the data element clearly states or defines the purpose of the data element, or the values used in the data element can be understood by metadata or data inspection. The metadata of the entity clearly states or defines the purpose of the entity and its required attributes/domains. |
B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| 1) A data value is a Valid Value or within a specified range of valid values for this data element.
2) Data values are consistent with the Attribute (Fact) definition. |
ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| This dimension refers to whether instances of data are represented in a format that is consistent with the domain of values and with other similar attribute values. For example, the display of time in a non-military (12-hour) format may be confusing if all other instances of times in the system are displayed in the 24-hour military format. | LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
| This dimension refers to whether instances of data are either store, exchanged, or presented in a format that is consistent with the domain of values, as well as consistent with other similar attribute values. Each column has numerous metadata attributes associated with it: its data type, precision, format patterns, use of a predefined enumeration of values, domain ranges, underlying storage formats, etc. | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
| Appropriate metadata is available to define, constrain, and document data. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
| Representation consistency refers to whether physical instances of data are in record with their formats. For example, an EMPLOYEE’s salary cannot be represented “$AXT,” as there is (or should be) no such element in S. One would often like to know whether a physical instance is the proper representation for the intended (correct) value. But in practice this is rarely possible, as the intended value is conceptual and not known. So one is left with the issue of whether the representation conflicts with S. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
Accuracy to reality
| Characteristic Name: | Accuracy to reality |
| Dimension: | Accuracy |
| Description: | Data should truly reflect the real world |
| Granularity: | Record |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to lack of accuracy to reality |
| The number of complaints received due to lack of accuracy to reality |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Continuously evaluate if the existing data model is sufficient to represent the real world as required by the organisational need and do the necessary amendments to the data model if needed. | (1) A student who received a concession travel card is not eligible for a concession fare if he terminates his candidature before completion of the course. Hence the data model should have an extra attribute as "current status of candidature" |
| Perform regular audits on mission critical data to verify that every record has a meaningful existence in the reality which is useful for the organisation | (1) All customers existing in the customer master file actually a customer in the customer space open for the organisation. (non customers are not in the customer file) (2) "Greg Glass" is recorded as a glass work company but in fact they are opticians (3) A person's personal details taken from his educational profile may not be a correct reality for his insurance profile even though the information is |
| Perform regular audits on mission critical data to verify that every record has a unique existence in the reality | (1) It is difficult to find out that the professor "Andrew" is from Colombia university or from the university of Queensland |
| Ensure that Information available in the system is accurate in the context of a particular activity or event | (1) The driver details taken from vehicle registration may not be accurate in the case of finding the real person who drive the vehicle when an accident is caused |
Validation Metric:
| How mature is the process to ensure the accuracy to reality |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| if the name of a person is John, the value v = John is correct, while the value v = Jhn is incorrect | C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006. |
| Percent of values that are correct when compared to the actual value. For example, M=Male when the subject is Male. | P. Cykana, A. Paul, and M. Stern, “DoD Guidelines on Data Quality Management” in MIT Conference on Information Quality - IQ, 1996, pp. 154-171. |
| an EMPLOYEE entity (identified by the Employee-Number
314159) and the attribute Year-of-Birth. If the value of Year-of-Birth for employee 314159 is the year the employee was born, the datum is correct. |
C. Fox, A. Levitin, and T. Redman, “The Notion of Data and Its Quality Dimensions” in Journal Information Processing and Management: an International Journal archive, Volume 30 Issue 1, Jan-Feb 1994, 1992, pp. 9-19. |
| Consider a database that contains names, addresses, phone numbers, and e- mail addresses of physicians in the state of Texas. This database is known to have a number of errors: some records are wrong, some are missing, and some are obsolete. If you compare the database to the true population of physicians, it is expected to be 85% accurate. If this database is to be used for the state of Texas to notify physicians of a new law regarding assisted suicide, it would certainly be considered poor quality. In fact, it would be dangerous to use it for that intended purpose.
24 2.1 Data Quality Definitions 25 If this database were to be used by a new surgical device manufacturer to find potential customers, it would be considered high quality. Any such firm would be delighted to have a potential customer database that is 85% accurate. From it, they could conduct a telemarketing campaign to identify real sales leads with a completely acceptable success rate. The same database: for one use it has poor data quality, and for another it has high data quality. |
J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003. |
| The patient’s identification details are correct and uniquely identify the patient. | P. J. Watson, “Improving Data Quality: A Guide for Developing Countries”, World Health Organization, 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Determines the extent to which data objects correctly represent the real-world values for which they were designed. For example, the sales orders for the Northeast region must be assigned a Northeast sales representative. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| The data value correctly reflects the real-world condition. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| The data correctly reflects the Characteristics of a Real-World Object or Event being described. Accuracy and Precision represent the highest degree of inherent Information Quality possible. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Is the information precise enough and close enough to reality? | EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer. |
| 1) Each identifiable data unit maps to the correct real-world phenomenon.
2) Non-identifying (i.e. non-key) attribute values in an identifiable data unit match the property values for the represented real-world phenomenon. 3) Each identifiable data unit represents at least one specific real-world phenomenon. 4) Each identifiable data unit represents at most one specific real-world phenomenon. |
PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
| 1) The degree to which an information object correctly represents another information object, process, or phenomenon in the context of a particular activity or culture.
2) Closeness of agreement between a property value and the true value (value that characterizes a characteristic perfectly defined in the conditions that exists when the characteristic is considered. 3) The extent to which the correctness of information is verifiable or provable in the context of a particular activity. |
STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |